Skip to content

Enhance capability hosts documentation #533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Enhance capability hosts documentation #533

wants to merge 1 commit into from

Conversation

karpikpl
Copy link
Contributor

Updated capability hosts documentation to include agent definitions in thread storage and emphasized resource region alignment.

@karpikpl
Enhance capability hosts documentation
2e1aa2f 
Updated capability hosts documentation to include agent definitions in thread storage and emphasized resource region alignment.
@prmerger-automator PRMerger Automator
Copy link
Contributor

@karpikpl : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod Learn Build Service (PROD)
Copy link
Contributor

Learn Build status updates of commit 2e1aa2f:

✅ Validation status: passed

File Status Preview URL Details
articles/ai-foundry/agents/concepts/capability-hosts.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@fosteramanda

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Aug 28, 2025
@karpikpl
Copy link
Contributor Author

I'm not sure about the changes anymore. It would be good to get clarification on region and resource placement requirements.

documentation from https://github.com/azure-ai-foundry/foundry-samples/tree/main/samples/microsoft/infrastructure-setup/15-private-network-standard-agent-setup states that:

Region and Resource Placement Requirements

  • All Foundry workspace resources should be in the same region as the VNet, including CosmosDB, Storage Account, AI Search, Foundry Account, Project, Managed Identity. The only exception is within the Foundry Account, you may choose to deploy your model to a different region, and any cross-region communication will be handled securely within our network infrastructure.
    • Note: Your Virtual Network can be in a different resource group than your Foundry workspace resources

but I was able to deploy workspace resources in another region and Agent Service is working
image

image

@v-dirichards
Copy link
Contributor

@fosteramanda Could you respond to the comment above?

@karpikpl
Copy link
Contributor Author

karpikpl commented Sep 5, 2025 •
edited
Loading

Azure Documentation has "must be"

Note

All Foundry workspace resources must be deployed in the same region as the virtual network (VNet). This includes Cosmos DB, Storage Account, AI Search, Foundry Account, Project, and Managed Identity.
Exception: You may connect your Foundry Project to models deployed in a different region (on another AI Foundry or Azure OpenAI resource) by configuring an appropriate AI Services connection on the Project's capability host.

but it works cross region 😕

Another contradiction - Foundry Agent Service documentation:

Note

To avoid cross-region bandwidth charges, deploy Azure Cosmos DB, Storage, and AI Search in the same Azure region as Foundry Agent Service.

which again, means that cross region should work, it's just going to be expensive

@github-actions GitHub Actions
Copy link

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Sep 19, 2025
@karpikpl
Copy link
Contributor Author

yeah, I'm done #sign-off
just waiting for Amandas feedback

@prmerger-automator PRMerger Automator
Copy link
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @fosteramanda

@github-actions github-actions bot removed the inactive This PR is inactive for more than 14 days label Sep 20, 2025
@github-actions GitHub Actions
Copy link

github-actions bot commented Oct 6, 2025

This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions.
Get Help
Docs Support Teams Channel
Resolve Merge Conflict

@github-actions github-actions bot added the inactive This PR is inactive for more than 14 days label Oct 6, 2025
@karpikpl
Copy link
Contributor Author

karpikpl commented Oct 6, 2025

Yeah, been waiting for a review for a long time

@github-actions github-actions bot removed the inactive This PR is inactive for more than 14 days label Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fosteramanda fosteramanda Awaiting requested review from fosteramanda

Assignees

@fosteramanda fosteramanda

Labels
aq-pr-triaged C+L Pull Request Review Team label azure-ai-agent-service/svc Change sent to author do-not-merge
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@karpikpl @v-dirichards @fosteramanda